Hardware platform based on fpga partial reconfiguration for wireless communication device

ABSTRACT

Systems and methods are disclosed herein that relate to partially reconfiguring a Field Programmable Gate Array (FPGA) of a wireless communication device to provide time-slicing of modem and application functionality. In this manner, a low-cost, small size, and low power consumption implementation of the FPGA and thus the wireless communication device is provided.

TECHNICAL FIELD

The present disclosure relates to a Field Programmable Gate Array (FPGA) hardware platform for a wireless communication device such as, e.g., a Machine Type Communication (MTC) device or Internet of Things (IoT) device.

BACKGROUND

By 2020, more than 50 billion devices are expected to be connected to the cloud in what is referred to as the Internet of Things (IoT). These devices in the IoT are referred to as IoT devices. To adapt different applications and radio access technologies, hardware and software implementation of IoT devices is required to be flexible. Due to its ability to be (re)programmed after manufacturing, a Field Programmable Gate Array (FPGA) is a good candidate for implementation of an IoT device. On the other hand, for most IoT devices, the cost, size, and power consumption are critical in order to deploy them on a great scale. However, designing a platform for an IoT device with low cost, small size, and low power consumption is challenging.

Chinese Patent Application Publication No. CN102523275 proposes an IoT access system based on an FPGA, particularly focusing on the system and hardware design. However, it fails to describe or mention any type of optimization of cost, area, and power consumption.

An FPGA is an integrated circuit that can be programmed or reprogrammed after manufacturing by a customer or designer. The FGPA is programmed using a Hardware Description Language (HDL). In particular, an HDL is used to define the behavior of the FPGA. Then, using an electronic design automation tool, a technology-mapped netlist is generated. The netlist is then fit to the FPGA architecture, usually using proprietary software of the FPGA manufacturer. Once design and validation is complete, the bit file, or binary file, generated by the proprietary software of the FPGA manufacturer is loaded into the FPGA via a serial interface or external memory. In this manner, the FPGA can be programmed or reprogrammed as desired.

Some FPGAs support partial reconfiguration. Partial reconfiguration of an FPGA refers to reconfiguring a portion of the reconfigurable hardware circuitry of the FPGA while the other part(s) of the reconfigurable hardware circuitry are still operating as previously programmed. In other words, partial reconfiguration allows some parts, or functionality, of the FPGA to continue operating while another part(s), or functionality, of the FPGA is reprogrammed. For example, if a data processing functionality implemented on an FPGA requires different types of algorithms for different types of input data, the functionality of the FPGA may be reconfigured as need while the rest of the FPGA continues to operate.

What is needed are systems and methods that leverage the flexibility of an FPGA to provide an IoT device with low cost, small size, and low power consumption.

SUMMARY

Systems and methods are disclosed herein that relate to partially reconfiguring a Field Programmable Gate Array (FPGA) of a wireless communication device to provide time-slicing of modem and application functionality. In some embodiments, a method for partially reconfiguring an FPGA that provides processing functionality for a wireless communication device comprises determining that a first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, where the modem functionality is functionality related to transmitting and/or receiving signals via a Radio Frequency (RF) transmit and/or receive circuitry that is external to the FPGA. The method further comprises, upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, loading a modem bit file into a reconfiguration partition of the FPGA, where the modem bit file programs the reconfiguration partition of the FPGA to provide the modem functionality. The method further comprises, after loading the modem bit file into the reconfiguration partition of the FPGA, determining that a second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred. The method further comprises, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, loading an application bit file into the reconfiguration partition of the FPGA, where the application bit file programs the reconfiguration partition of the FPGA to provide the application functionality. In this manner, time-slicing of the modem and application functionality is provided, which enables a low-cost, small size, and low power consumption implementation of the FPGA and thus the wireless communication device.

In some embodiments, the wireless communication device periodically transmits and/or receives signals via a wireless communication network, and the first triggering event is an event indicative of a start of a transmit and/or receive occasion of the wireless communication device. Further, in some embodiments, the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.

In some embodiments, the wireless communication device periodically transmits and/or receives signals via a wireless communication network, and the first triggering event is expiration of a timer having a duration equal to an amount of time between transmit and/or receive occasions for the wireless communication device. Further, in some embodiments, expiration of the timer is indicative of a start of a transmit and/or receive occasion of the wireless communication device, and the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.

In some embodiments, the application functionality comprises functionality to process signals received and stored by the FPGA while the reconfiguration partition was programmed to provide the modem functionality and/or functionality to collect data from one more sensors that are external to the FPGA.

In some embodiments, the method further comprises, upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, enabling an interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to the RF transmit and/or receive circuitry. Further, in some embodiments, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, disabling the interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to the RF transmit and/or receive circuitry.

In some embodiments, the method further comprises, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, enabling an interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to one or more external sensors.

In some embodiments, the method further comprises, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, waiting a predefined amount of time prior to loading the application bit file into the reconfiguration partition of the FPGA.

In some embodiments, the method further comprises, prior to determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, loading a main bit file into a main partition of the FPGA that programs the main partition of the FPGA to provide a processor, a timer, memory, an interface to the RF transmit and/or receive circuitry, and an interface to the one or more external sensors.

In some embodiments, the method is performed by one or more components of the FPGA.

In some embodiments, the method is performed by a controller that is external to the FPGA.

In some embodiments, a wireless communication device for operation in a wireless communication network comprises RF transmit and/or receive circuitry, one or more sensors, non-volatile memory storing a modem bit file and an application bit file, and an FPGA. A controller is operable to determine that a first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, where the modem functionality is functionality related to transmitting and/or receiving signals via the RF transmit and/or receive circuitry. The controller is further operable to, upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, load the modem bit file from the non-volatile memory into a reconfiguration partition of the FPGA, where the modem bit file programs the reconfiguration partition of the FPGA to provide the modem functionality. The controller is further operable to, after loading the modem bit file into the reconfiguration partition of the FPGA, determine that a second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred. The controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, load the application bit file from the non-volatile memory into the reconfiguration partition of the FPGA, where the application bit file programs the reconfiguration partition of the FPGA to provide the application functionality.

In some embodiments, the non-volatile memory further stores a main bit file and the controller is further operable to, prior to determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, load the main bit file into a main partition of the FPGA that programs the main partition of the FPGA to provide memory, an interface to the RF transmit and/or receive circuitry, and an interface to the one or more sensors.

In some embodiments, the controller is implemented within the FPGA.

In some embodiments, the controller is a component of the wireless communication device and is external to the FPGA.

In some embodiments, the wireless communication device periodically transmits and/or receives signals via the wireless communication network, and the first triggering event is an event indicative of a start of a transmit and/or receive occasion of the wireless communication device. Further, in some embodiments, the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.

In some embodiments, the wireless communication device periodically transmits and/or receives signals via the wireless communication network, and the first triggering event is expiration of a timer having a duration equal to an amount of time between transmit and/or receive occasions for the wireless communication device. Further, in some embodiments, expiration of the timer is indicative of a start of a transmit and/or receive occasion of the wireless communication device, and the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.

In some embodiments, the application functionality comprises functionality to process signals received and stored by the FPGA while the reconfiguration partition was programmed to provide the modem functionality and/or functionality to collect data from one more sensors that are external to the FPGA.

In some embodiments, the controller is further operable to, upon determining that the first triggering event for partially reconfiguring the FPGA to provide the modem functionality has occurred, enable the interface to the RF transmit and/or receive circuitry. Further, in some embodiments, the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, disable the interface to the RF transmit and/or receive circuitry.

In some embodiments, the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, enable the interface to the one or more sensors.

In some embodiments, the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, wait a predefined amount of time prior to loading the application bit file into the reconfiguration partition of the FPGA.

Those skilled in the art will appreciate the scope of the present disclosure and realize additional aspects thereof after reading the following detailed description of the embodiments in association with the accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

FIG. 1 illustrates a conventional Internet of Things (IoT) device using a Field Programmable Gate Array (FPGA) hardware platform;

FIG. 2 illustrates a wireless communication device (e.g., a Machine Type Communication (MTC) device or IoT device) using an FPGA hardware platform that utilizes time-slicing of modem and application functionality via partial reconfiguration of the FPGA according to some embodiments of the present disclosure;

FIG. 3 is a flow chart that illustrates the operation of a controller(s) to control partial reconfiguration of the FPGA of the wireless communication device of FIG. 2 to provide time-slicing between the modem and the application in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates one example of the Radio Frequency (RF) interface of the FPGA of the wireless communication device of FIG. 2 that includes a mechanism for enabling and disabling the RF interface according to some embodiments of the present disclosure; and

FIG. 5 illustrates one example of the sensor interface of the FPGA of the wireless communication device of FIG. 2 that includes a mechanism for enabling and disabling the sensor interface according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

Systems and methods are disclosed herein that provide a Field Programmable Gate Array (FPGA) based hardware platform for a wireless communication device (e.g., a Machine Type Communication (MTC) device such as, e.g., an Internet of Things (IoT) device). In particular, partial reconfiguration of the FPGA is applied to time-slice the FPGA to provide modem functionality and application functionality separately. As a result, the design can fit into a much smaller FPGA and a low-cost, small-size, and low power consumption wireless communication device can be achieved.

Before describing embodiments of the present disclosure, a brief discussion of a conventional FPGA hardware platform for an IoT device is beneficial. As illustrated in FIG. 1, a conventional IoT device 10 using an FPGA hardware platform includes an FPGA 12, non-volatile memory 14, Radio Frequency (RF) transmit (TX) and/or receive (RX) circuitry 16, and a power and board test block 18 connected to a circuit board 20. A full bit file 22 is stored in the non-volatile memory 14 and loaded into the FPGA 12 via a controller on the FPGA 12 (not shown) or an external controller either on the circuit board 20 or external to the circuit board 20. The full bit file 22 is a binary file that, once loaded into the FPGA 12, programs the FPGA 12 to provide defined functionality. In this example, the full bit file 22 programs, or configures, the FPGA 12 to include:

-   -   a modem 24 that, e.g.,         -   performs digital baseband processing (e.g., modulation) for             signals transmitted via the RF TX and/or RX circuitry 16,         -   performs digital baseband processing (e.g., demodulation)             for signals received via the RF TX and/or RX circuitry 16,         -   fetching data output by an application 26 and processing the             data for, e.g., transmission via the RF TX and/or RX             circuitry 16, and/or         -   receive commands from, e.g., an IoT server or another IoT             device(s) via the RF TX and/or RX circuitry 16 and process             the received commands,     -   an application 26 that provides application-level functionality         (e.g., data processing logic) such as, e.g.,         -   collecting data from one or more sensors 28-1 through 28-N             (generally referred to herein individually as sensor 28 and             collectively as sensors 28) that are, in this example,             external to the circuit board 20,         -   storing the collected data in Static Random Access Memory             (SRAM) 30,         -   performing data compression for collected data,         -   performing data cryptography for the collected data, and/or         -   providing collected data to an external device, e.g., an             external display,     -   an RF interface 32 that communicatively couples the modem 24 to         the RF TX and/or RX circuitry 16,     -   a sensor interface 34 that communicatively couples the         application 26 to the one or more sensors 28,     -   the SRAM 30 or other type of volatile memory that, e.g., stores         data collected or otherwise output by the application 26, and     -   a timer 36 that is always on and schedules the RF sleep/wake         switching so that the IoT device 10 can listen to the wireless         communication network and transmit/receive data.

Note that both the modem 24 and the application 26 can be integrated into a single FPGA component.

In the example of FIG. 1, on power-up, the full bit file 22 is loaded into the FPGA 12. The may be done via a self-loading mechanism (i.e., the full bit file 22 is loaded by the FPGA 12 itself) or via an external controller (e.g., a controller in the power and board test block 18).

FIG. 2 illustrates a wireless communication device 38 using an FPGA hardware platform that utilizes time-slicing of modem and application functionality via partial reconfiguration of the FPGA according to some embodiments of the present disclosure. The wireless communication device 38 may be, e.g., an MTC device or more specifically an IoT device. The wireless communication device 38 is for operation in a wireless communication system such as, e.g., a cellular communications network such as, e.g., a Fifth Generation (5G) cellular communications network that supports, e.g., a narrowband IoT network.

As illustrated, the wireless communication device 38 includes an FPGA 40, non-volatile memory 42, RF TX and/or RX circuitry 44, and a power and board test block 46 connected to a circuit board 48. In order to support time-slicing of modem and application functionality via partial reconfiguration of the FPGA 40, a main bit file 52, a modem bit file 54, and an application (app) bit file 56 are stored in the non-volatile memory 42. Partial reconfiguration of the FPGA 40 allows parts of the FPGA 40 to be reconfigured, or reprogrammed, without interrupting other running parts of the FPGA 40. This enables specialized modules (i.e., a modem as defined by the modem bit file 54 and an application as defined by the application bit file 56) to be loaded on-demand at run time without occupying chip space when they are inactive.

The main bit file 52 is a binary file that, once loaded into the FPGA 40, configures a subset of the reconfigurable hardware resources (e.g., resources referred to herein as a main partition) to provide defined main or core functionality of the FPGA 40 that continues to operate even during partial reconfiguration. The modem bit file 54 and the application bit file 56 are separate binary files that, when loaded into a reconfiguration partition 58 of the FPGA 40, partially reconfigure the FPGA 40 such that the reconfiguration partition 58 is configured as a modem that provides modem functionality or an application that provides application functionality, respectively. The main bit file 52 is loaded into the FPGA 40 at power-up by a controller on the FPGA 40 or an external controller either on the circuit board 48 or external to the circuit board 48. The modem bit file 54 and the application bit file 56 are loaded into the FPGA 40 on-demand by a controller on the FPGA 40 or an external controller either on the circuit board 48 or external to the circuit board 48 to provide partial reconfiguration of the FPGA 40, as described below. In this example, the main bit file 52 is loaded into the FPGA 40 on power-up and programs, or configures, the FPGA 40 to include the reconfiguration partition 58, a microprocessor 60, a Partial Reconfiguration Interface (PR IF) 62, a timer 64, SRAM 66 (or other type of volatile memory), an RF interface 68, and a sensor interface 70. Further, in this example, the microprocessor 60 controls on-demand loading of the modem bit file 54 and the application bit file 56 into the reconfiguration partition 58 to provide time-slicing of the modem and application, as described below.

The reconfiguration partition 58 is a subset of the reconfigurable hardware resources of the FPGA 40 allocated for partial reconfiguration. As discussed below, the reconfiguration partition 58 is reconfigured by loading either the modem bit file 54 or the application bit file 56, as described below.

In this example, the microprocessor 60 operates to control on-demand loading of the modem bit file 54 and the application bit file 56 into the reconfiguration partition 58 to provide time-slicing of the modem and application, as described below. The microprocessor 60 receives input (e.g., interrupts) from the timer 64 to trigger partial configuration. The microprocessor 60 configures the reconfiguration partition 58 (i.e., loads a bit file into the reconfiguration partition 58) via the PR IF 62.

The timer 64 is always on and schedules the RF sleep/wake switching so that the wireless communication device 38 can listen to the wireless communication network and transmit/receive data. More specifically, in some embodiments, the wireless communication device 38 wakes up at defined times (e.g., periodically) to transmit and/or receive signals via the RF TX and/or RX circuitry 44. The time periods in which the wireless communication device 38 wakes up to transmit and/or receive signals via the RF TX and/or RX circuitry 44 are referred to herein as transmit and/or receive occasions. The start of a transmit and/or receive occasion, as indicated by the timer 64, is a triggering event that triggers partial reconfiguration of the FPGA 40 by loading the modem bit file 54 into the reconfiguration partition 58 such that the reconfiguration partition 58 operates as a modem that provides modem functionality, rather than an application that provides application functionality. Similarly, the end of a transmit and/or receive occasion is an event that triggers partial reconfiguration of the FPGA 40 by loading the application bit file 56 into the reconfiguration partition 58 such that the reconfiguration partition 58 operates as an application that provides application functionality, rather than a modem that provides modem functionality. In some embodiments, the timer 64 generates interrupt signals to the microprocessor 60 to indicate the start of a transmit and/or receive occasion and the end of the transmit and/or receive occasion. In response to these interrupt signals, the microprocessor 60 loads the appropriate bit files 54 or 56 into the reconfiguration partition 58.

The SRAM 66 is volatile memory used to store data shared between the modem and the application.

The RF interface 68 communicatively couples the reconfiguration partition 58, and in particular the modem when the reconfiguration partition 58 is configured as a modem, to the RF TX and/or RX circuitry 44. In some embodiments, the microprocessor 60 enables the RF interface 68 during transmit and/or receive occasions and otherwise disables the RF interface 68.

The sensor interface 70 communicatively couples the reconfiguration partition 58, and in particular the application when the reconfiguration partition 58 is configured as an application, to one or more sensors 72-1 through 72-N (generally referred to herein individually as sensor 72 and collectively as sensors 72) that are, in this example, external to the circuit board 48. The sensors 72 may include any type(s) of sensor such as, e.g., a temperature sensor(s), a pressure sensor(s), a water sensor(s), a gas sensor(s), etc., and/or the like.

FIG. 3 is a flow chart that illustrates the operation of a controller(s) to control partial reconfiguration of the FPGA 40 of the wireless communication device 38 to provide time-slicing between the modem and the application in accordance with some embodiments of the present disclosure. Optional steps are indicated with dashed boxes. This process may be performed by a controller on the FPGA 40 (e.g., the microprocessor 60) or by some controller that is external to the FPGA 40 (e.g., a controller in the power and board test block 46) or some combination thereof.

As illustrated, the main bit file 52 is loaded from the non-volatile memory 42 into the FPGA 40 (step 100). In the example of FIG. 2, the main bit file 52 programs, or configures, a subset of the reconfigurable hardware resources of the FPGA 40 to provide the reconfiguration partition 58, the microprocessor 60, the PR IF 62, the timer 64, the SRAM 66 (or other type of volatile memory), the RF interface 68, and the sensor interface 70. A controller (e.g., the microprocessor 60) determines whether an RF ON event has occurred (step 102). The RF ON event is an event that indicates the start of a TX and/or RX occasion of the wireless communication device 38. For example, the RF ON event may be the expiration of a timer having a duration equal to an amount of time between periodic transmit and/or receive occasions for the wireless communication device 38. More specifically, in some embodiments, the timer 64 determines when a TX and/or RX occasion of the wireless communication device 38 is to start (e.g., upon expiration of a corresponding timer) and sends an interrupt to the microprocessor 60 to thereby trigger the microprocessor 60 to perform partial reconfiguration.

Upon detecting an RF ON event, the controller (e.g., the microprocessor 60) loads the modem bit file 54 into the reconfiguration partition 58 of the FPGA 40 via the PR IF 62 (step 104) and, optionally (i.e., in some embodiments), enables the RF interface 68 (step 106). Note that, in some embodiments, both the RF interface 68 and the sensor interface 70 are disabled during partial reconfiguration. In step 106, the RF interface 68 is then enabled after partial reconfiguration is complete.

At this point, the reconfiguration partition 58 of the FPGA 40 is configured as a modem that provides modem functionality. The modem functionality includes, e.g., performing digital baseband processing (e.g., modulation) for signals transmitted via the RF TX and/or RX circuitry 44, performing digital baseband processing (e.g., demodulation) for signals received via the RF TX and/or RX circuitry 44, fetching data output by the application (while the reconfiguration partition 58 was previously configured as an application) from the SRAM 66 and processing the data for, e.g., transmission via the RF TX and/or RX circuitry 44, and/or receive command(s) from, e.g., an IoT server or another IoT device(s) via the RF TX and/or RX circuitry 44 and processing the received command(s).

While the reconfiguration partition 58 is configured as a modem, the controller (e.g., the microprocessor 60) monitors for an RF OFF event (step 108). The RF OFF event is an event that indicates the completion, or end, of the TX and/or RX occasion of the wireless communication device 38. For example, the RF OFF event may be the expiration of a timer having a duration equal to a length (in time) of the TX and/or RX occasion. More specifically, in some embodiments, the timer 64 determines when the TX and/or RX occasion of the wireless communication device 38 is to end (e.g., upon expiration of a corresponding timer) and sends an interrupt to the microprocessor 60 to thereby trigger the microprocessor 60 to perform partial reconfiguration.

Upon detecting an RF OFF event, the controller (e.g., the microprocessor 60) optionally waits for some predefined amount of time, e.g., to ensure that modem operations are complete (step 110), optionally disables the RF interface 68 (step 112), loads the application bit file 56 into the reconfiguration partition 58 of the FPGA 40 via the PR IF 62 (step 114), and optionally enables the sensor interface 70 (step 116).

At this point, the reconfiguration partition 58 of the FPGA 40 is configured as an application that provides application functionality. The application functionality includes, e.g., collecting data from the one or more sensors 72 that are, in this example, external to the circuit board 48, storing the collected data in the SRAM 66, performing data compression for the collected data, performing data cryptography for the collected data, and/or providing the collected data to an external device, e.g., an external display.

The process returns to step 102 and is repeated. Note that, while not illustrated, the SRAM 66 is disabled during partial reconfiguration and enabled after partial reconfiguration is complete (i.e., disabled prior to step 104 and enabled after step 104 is complete and again disabled prior to step 114 and enabled after step 114 is complete). In the example of FIG. 2, the SRAM 66 is enabled and disabled via a respective enable signal (EN_SRAM) provided by the microprocessor 60.

Again, while steps 102 through 116 (and optionally step 100) are performed by the microprocessor 60 on the FPGA 40 in the example of FIG. 2, the present disclosure is not limited thereto. For example, some or all of step 102 through 116 (and optionally 100) may be performed by a controller that is on the circuit board 48 but external to the FPGA 40, by a controller that is external to (i.e., not on) the circuit board 48, or a finite state machine.

FIGS. 4 and 5 illustrate example embodiments of mechanisms with the RF interface 68 and the sensor interface 70 that allow the interfaces 68 and 70, respectively, to be enabled and disabled according to some embodiments of the present disclosure. More specifically, in the example of FIG. 4, the RF interface 68 includes a first AND gate 74 that passes the RX signal from the RF TX and/or RX circuitry 44 to the reconfiguration partition 58 when a respective enable signal (EN_RF_IF) is asserted. The RF interface 68 also includes a second AND gate 76 that passes the TX signal from the reconfiguration partition 58 to the RF TX and/or RX circuitry 44 when the respective enable signal (EN_RF_IF) is asserted. As illustrated in FIG. 5, the sensor interface 70 includes an AND gate 78 that passes a sensor interface output signal to the reconfiguration partition 58 when a respective enable signal (EN_SENSOR_IF) is asserted. The sensor interface output signal is, e.g., a signal that includes data from any one or more of the sensors 72.

The following acronyms are used throughout this disclosure.

5G Fifth Generation FPGA Field Programmable Gate Array HDL Hardware Description Language loT Internet of Things MTC Machine Type Communication PR IF Partial Reconfiguration Interface RF Radio Frequency RX Receive SRAM Static Random Access Memory TX Transmit

Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow. 

1. A method for partially reconfiguring a Field Programmable Gate Array, FPGA, that provides processing functionality for a wireless communication device, comprising: determining that a first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, the modem functionality being functionality related to transmitting and/or receiving signals via a radio frequency transmit and/or receive circuitry that is external to the FPGA; upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, loading a modem bit file into a reconfiguration partition of the FPGA, the modem bit file programming the reconfiguration partition of the FPGA to provide the modem functionality; after loading the modem bit file into the reconfiguration partition of the FPGA, determining that a second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred; and upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, loading an application bit file into the reconfiguration partition of the FPGA, the application bit file programming the reconfiguration partition of the FPGA to provide the application functionality.
 2. The method of claim 1 wherein the wireless communication device periodically transmits and/or receives signals via a wireless communication network, and the first triggering event is an event indicative of a start of a transmit and/or receive occasion of the wireless communication device.
 3. The method of claim 2 wherein the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.
 4. The method of claim 1 wherein the wherein the wireless communication device periodically transmits and/or receives signals via a wireless communication network, and the first triggering event is expiration of a timer having a duration equal to an amount of time between transmit and/or receive occasions for the wireless communication device.
 5. The method of claim 4 wherein expiration of the timer is indicative of a start of a transmit and/or receive occasion of the wireless communication device, and the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.
 6. The method of claim 1 wherein the application functionality comprises: functionality to process signals received and stored by the FPGA while the reconfiguration partition was programmed to provide the modem functionality; and/or functionality to collect data from one more sensors that are external to the FPGA.
 7. The method of claim 1 further comprising, upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, enabling an interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to the radio frequency transmit and/or receive circuitry.
 8. The method of claim 7 further comprising, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, disabling the interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to the radio frequency transmit and/or receive circuitry.
 9. The method of claim 1 further comprising, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, enabling an interface on the FPGA that communicatively couples the reconfiguration partition of the FPGA to one or more external sensors.
 10. The method of claim 1 further comprising, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, waiting a predefined amount of time prior to loading the application bit file into the reconfiguration partition of the FPGA.
 11. The method of claim 1 further comprising, prior to determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, loading a main bit file into a main partition of the FPGA that programs the main partition of the FPGA to provide a processor, a timer, memory, an interface to the radio frequency transmit and/or receive circuitry, and an interface to the one or more external sensors.
 12. The method of claim 1 wherein the method is performed by one or more components of the FPGA.
 13. The method of claim 1 wherein the method is performed by a controller that is external to the FPGA.
 14. A wireless communication device for operation in a wireless communication network, comprising: radio frequency transmit and/or receive circuitry; one or more sensors; non-volatile memory storing a modem bit file and an application bit file; and a Field Programmable Gate Array, FPGA; wherein a controller is operable to: determine that a first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, the modem functionality being functionality related to transmitting and/or receiving signals via the radio frequency transmit and/or receive circuitry; upon determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, load the modem bit file from the non-volatile memory into a reconfiguration partition of the FPGA the modem bit file programming the reconfiguration partition of the FPGA to provide the modem functionality; after loading the modem bit file into the reconfiguration partition of the FPGA, determine that a second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred; and upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, load the application bit file from the non-volatile memory into the reconfiguration partition of the FPGA, the application bit file programming the reconfiguration partition of the FPGA to provide the application functionality.
 15. The wireless communication device of claim 14 wherein: the non-volatile memory further stores a main bit file; and the controller is further operable to, prior to determining that the first triggering event for partially reconfiguring the FPGA to provide modem functionality has occurred, load the main bit file into a main partition of the FPGA that programs the main partition of the FPGA to provide memory, an interface to the radio frequency transmit and/or receive circuitry, and an interface to the one or more sensors.
 16. The wireless communication device of claim 14 wherein the controller is implemented within the FPGA.
 17. The wireless communication device of claim 14 wherein the controller is a component of the wireless communication device and is external to the FPGA.
 18. The wireless communication device of claim 14 wherein the wireless communication device periodically transmits and/or receives signals via the wireless communication network, and the first triggering event is an event indicative of a start of a transmit and/or receive occasion of the wireless communication device.
 19. The wireless communication device of claim 18 wherein the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.
 20. The wireless communication device of claim 14 wherein the wireless communication device periodically transmits and/or receives signals via the wireless communication network, and the first triggering event is expiration of a timer having a duration equal to an amount of time between transmit and/or receive occasions for the wireless communication device.
 21. The wireless communication device of claim 20 wherein expiration of the timer is indicative of a start of a transmit and/or receive occasion of the wireless communication device, and the second triggering event is an event indicative of completion of the transmit and/or receive occasion of the wireless communication device.
 22. The wireless communication device of claim 14 wherein the application functionality comprises: functionality to process signals received and stored by the FPGA while the reconfiguration partition was programmed to provide the modem functionality; and/or functionality to collect data from one more sensors that are external to the FPGA.
 23. The wireless communication device of claim 15 wherein the controller is further operable to, upon determining that the first triggering event for partially reconfiguring the FPGA to provide the modem functionality has occurred, enable the interface to the radio frequency transmit and/or receive circuitry.
 24. The wireless communication device of claim 23 wherein the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, disable the interface to the radio frequency transmit and/or receive circuitry.
 25. The wireless communication device of claim 15 wherein the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, enable the interface to the one or more sensors.
 26. The wireless communication device of claim 14 wherein the controller is further operable to, upon determining that the second triggering event for partially reconfiguring the FPGA to provide application functionality, rather than the modem functionality, has occurred, wait a predefined amount of time prior to loading the application bit file into the reconfiguration partition of the FPGA. 